Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1263

reference: 701-tree-1
name: 1263
tree-preservation-order: undefined
701-tpo-1
uprn
address-text
point: POINT (-1.007635 50.887581)
geometry: MULTIPOLYGON (((-1.007564 50.887573,-1.007567 50.887587,-1.007577 50.887600,-1.007593 50.887610,-1.007612 50.887617,-1.007634 50.887619,-1.007656 50.887617,-1.007676 50.887611,-1.007692 50.887601,-1.007703 50.887589,-1.007706 50.887575,-1.007703 50.887561,-1.007693 50.887548,-1.007678 50.887538,-1.007658 50.887531,-1.007636 50.887529,-1.007614 50.887531,-1.007594 50.887537,-1.007578 50.887547,-1.007568 50.887560,-1.007564 50.887573)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL